Skip to content

Configure Mend Bolt for GitHub#15

Open
mend-bolt-for-github[bot] wants to merge 1 commit intomasterfrom
whitesource/configure
Open

Configure Mend Bolt for GitHub#15
mend-bolt-for-github[bot] wants to merge 1 commit intomasterfrom
whitesource/configure

Conversation

@mend-bolt-for-github
Copy link
Copy Markdown

Welcome to Mend Bolt for GitHub (formerly WhiteSource). This is an onboarding PR to help you understand and configure settings before Mend starts scanning your repository for security vulnerabilities.

🚦 Mend Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable Mend Bolt for GitHub, simply close this Pull Request.


What to Expect

This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, Mend Bolt for GitHub will use the default configuration.

Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, Mend Bolt for GitHub will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.

If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.


❓ Got questions? Check out Mend Bolt for GitHub docs.
If you need any further assistance then you can also request help here.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

entelligence-ai-pr-reviews Bot commented Apr 30, 2026

EntelligenceAI PR Summary

This PR adds a Mend (WhiteSource) security scanning configuration file to automate dependency vulnerability detection and reporting.

  • Introduced .whitesource configuration file for Mend security scanning
  • Configured check run failures triggered on vulnerability detection
  • Enabled diff display mode for vulnerability results
  • Set issue reporting threshold to LOW severity, capturing all severity levels (LOW, MEDIUM, HIGH, CRITICAL)

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR introduces a .whitesource configuration file that enables Mend Bolt security scanning with sensible defaults, including LOW severity threshold to capture all vulnerability levels and diff display mode for clear reporting. The configuration is purely additive infrastructure with no impact on application logic, runtime behavior, or existing code paths. No issues were identified in the review, and the settings chosen (fail on vulnerability detection, report all severities) reflect a conservative and security-conscious posture appropriate for a production codebase.

Key Findings:

  • The .whitesource file is a declarative configuration with no executable code, eliminating any risk of introducing logic bugs or runtime errors.
  • Setting minSeverityLevel to LOW ensures the broadest possible vulnerability coverage, which is the correct conservative default for a security scanning tool.
  • The checkRunFailure setting being enabled means the CI pipeline will actively block merges on detected vulnerabilities, which strengthens the security posture of the repository rather than weakening it.
Files requiring special attention
  • .whitesource

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR introduces a Mend (WhiteSource) security scanning configuration file to enable automated dependency vulnerability scanning. The configuration sets up check run failures on detected vulnerabilities, enables diff display mode, and configures issue reporting for all severity levels starting from LOW.

Changes

File(s) Summary
.whitesource Added Mend (WhiteSource) security scanning configuration enabling dependency vulnerability scanning, check run failures on vulnerabilities, diff display mode, and issue reporting for all severities from LOW and above.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Repo as "GitHub Repository"
    participant Mend as "Mend Scanning Service"
    participant CI as "GitHub Check Runs"
    participant Issues as "Issue Tracker"

    Note over Repo: mendupdater.json config added
    Note over Repo: scanSettings, checkRunSettings,<br/>issueSettings defined
    Repo->>Mend: Trigger scan on PR / base branch
    activate Mend

    Mend->>Repo: Read mendupdater.json config
    Repo-->>Mend: scanSettings { baseBranches: [] }<br/>checkRunSettings { displayMode: "diff",<br/>useMendCheckNames: true }<br/>issueSettings { minSeverity: LOW,<br/>issueType: DEPENDENCY }

    Mend->>Mend: Run dependency scan

    alt Vulnerable dependencies found
        Mend->>CI: Create Check Run (Mend check name)<br/>conclusion: "failure"
        Note right of CI: Display mode: diff<br/>(only show new issues)
        CI-->>Mend: Check run created
        Mend->>Issues: Report issues<br/>minSeverity >= LOW, type: DEPENDENCY
        Issues-->>Mend: Issues logged
    else No vulnerabilities found
        Mend->>CI: Create Check Run<br/>conclusion: "success"
        CI-->>Mend: Check run created
    end

    deactivate Mend
    Mend-->>Repo: Scan complete
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants